Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference
318-tree-1
name
1182
tree-preservation-order

undefined

318-tpo-1
uprn
address-text
point
POINT (-1.029620 50.866347)
geometry
MULTIPOLYGON (((-1.029549 50.866339,-1.029553 50.866353,-1.029562 50.866366,-1.029578 50.866376,-1.029598 50.866382,-1.029620 50.866385,-1.029642 50.866383,-1.029661 50.866376,-1.029677 50.866366,-1.029688 50.866354,-1.029691 50.866340,-1.029688 50.866326,-1.029678 50.866314,-1.029663 50.866304,-1.029643 50.866297,-1.029621 50.866295,-1.029599 50.866297,-1.029579 50.866303,-1.029564 50.866313,-1.029553 50.866325,-1.029549 50.866339)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL